Systems and methods for load balancing devices connected to a base station via a network repeater

ABSTRACT

In some implementations, a device may obtain load information indicating a load of a first base station, wherein the load is associated with devices connected to the first base station. The device may determine that the load satisfies a load threshold of the first base station. The device may determine that a network repeater is connected to the first base station. The device may determine that a plurality of devices are connected to the network repeater. The device may determine that the network repeater is capable of connecting to a second base station. The device may cause the network repeater to connect to the second base station to reduce the load based on: the load satisfying the load threshold, the plurality of devices being connected to the network repeater, and the network repeater being capable of connecting to the second base station.

BACKGROUND

A network repeater or a network extender (referred to hereinafter as anetwork repeater) can be used to densify a network and provide coverageto areas where there may have been poor radio frequency (RF) coverage.Thus, network repeaters may add network density in terms of coverage,but not in terms of physical infrastructure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1E are diagrams of an example associated with load balancingdevices connected to a base station via a network repeater.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2 .

FIG. 4 is a flowchart of an example process relating to load balancingdevices connected to a base station via a network repeater.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Network repeaters may be used to extend coverage of millimeter wavesignals since a free space path loss (FSPL) of frequencies in themillimeter wavelength may be much higher than that used in otherwireless communication networks. Network repeaters may be a preferredchoice of extending network coverage since network repeaters do not needbackhaul nor require an expensive installation process as that of a basestation. Network repeaters may utilize beam steering technology and,when deployed, may require information, such as, power detectioninformation (e.g., a received signal strength indicator (RSSI), areference signal received power (RSRP), and/or the like), to ensureproper beam alignment from the network repeater to a base station (e.g.,a 5G next generation NodeB, also referred to as gNB). The networkrepeaters may utilize the required information to commission andproperly setup the correct beam from the network repeaters to thecorrect beam from the base station to establish the best possibleconnection.

A base station may be connected to a plurality of devices. In someinstances, the plurality of devices may include a network repeater thatis connected to multiple devices of a user. When a load of the basestation exceeds a maximum load, the base station may disconnect from oneor more devices of the plurality of devices. For example, the basestation may drop a call. As a result of disconnecting, the one or moredevices may experience poor network performance (e.g., experiencejitter, packet loss, among other examples). In some instances, the oneor more devices may attempt to re-establish a connection with the basestation. Attempting to re-establish a connection consumes networkresources, computing resources, among other examples.

Implementations described herein are directed to reducing a load of afirst base station by causing a network repeater to be disconnected fromthe first base station and to be connected to a second base station. Forexample, based on determining that the load of the first base station isapproaching a maximum load, a load management system may determinewhether a network repeater is connected to the first base station. Basedon determining that the network repeater is connected to the first basestation, the load management system may determine a load of the networkrepeater and determine whether the network repeater is able to connectto the second base station. The load management system may cause thenetwork repeater to disconnect from the first base station and toconnect to the second base station to reduce the load of the first basestation based on the load of the first base station, the load of thenetwork repeater, and/or determining that the network repeater is ableto connect to the second base station.

By causing the network repeater to connect to the second base station inthis manner, the implementations described herein may prevent the loadof the first base station from reaching the maximum load and,accordingly, prevent the first base station from being overloaded. As aresult of preventing the first base station from being overloaded, theimplementations described herein may prevent the first base station fromdisconnecting from one or more devices. By preventing the first basestation from disconnecting from the one or more devices, theimplementations described herein may prevent poor network performance.Additionally, by preventing the first base station from disconnectingfrom the one or more devices, the implementations described herein maypreserve network resources, computing resources, and/or other resourcesthat would been otherwise consumed in order to re-establish a connectionwith the first base station or any base station.

FIGS. 1A-1E are diagrams of an example implementation 100 associatedwith associated with load balancing devices connected to a base stationvia a network repeater. As shown in FIGS. 1A-1E, example implementation100 includes a network repeater 105 (e.g., a 5G network repeater), aneNodeB (eNB) 110, multiple gNBs 115 (referred to herein individually asgNB 115 or collectively as gNBs 115), multiple devices 120 (referred toherein individually as device 120 or collectively as devices 120), aload management system 125, a base station data structure 130, and anetwork repeater data structure 135. These devices are described in moredetail below in connection with FIG. 2 and FIG. 3 .

The network repeater 105 may include a device that focuses a wirelesssignal toward a receiving device (e.g., the eNB 110 or a gNB 115) tocreate a direct, fast, and reliable connection. For example, the networkrepeater 105 may include a network repeater (e.g., a device used toexpand coverage of a network and/or to offset a cost of an additionaleNB 110 and/or gNB 115), a dwelling repeater (e.g., a device used toextend mmWave coverage from outdoors to indoors), a commercial signalbooster, an industrial signal booster, among other examples.

The network repeater 105 may utilize beam forming technology toestablish a link with gNBs 115 to re-amplify and re-transmit mmWavecommunication signals. In this way, the network repeater 105 may extendthe RF coverage of the gNB 115, which may be limited due to power, FSPL,building infrastructures, foliage, and/or other types of natural and/orman-made elements. Thus, the network repeater 105 may allow for networkdensification and expansion without the cost and overhead of additionalbase stations.

In some examples, the network repeater 105 may automatically attach tothe eNB 110 or a gNB 115 when powered on. The network repeater 105 mayinclude a communication component (e.g., a CAT M1 module, a CAT1 module,a CAT3 module, a CAT4 modules, a WiFi module, among other examples) and,when initially powered on, the network repeater 105 may utilize thecommunication component to connect to a network via a closest eNB or aclosest gNB.

As shown in FIG. 1A, multiple devices 120 (referred to hereinindividually as device 120 or collectively as devices 120) may beconnected to the network repeater 105. The devices 120 may include adevice 120-1 (e.g., a virtual reality headset), a device 120-2 (e.g., afirst user equipment (UE)), a device 120-3 (e.g., a customer premiseequipment (CPE)), and/or a device 120-4 (e.g., a second UE). The networkrepeater 105 may be configured to enable devices 120 to establish aconnection with the eNB 110 and/or one or more gNBs 115.

The eNB 110 may include one or more devices capable of transferringtraffic, such as audio, video, text, and/or other traffic and may beassociated with a Long Term Evolution (LTE) or fourth generation (4G)network. The gNB 115 may include one or more devices that support, forexample, a cellular radio access technology (RAT) and wirelesscommunication for the network repeater 105. In some implementations,multiple gNBs 115 may be connected to a same eNB. For example, as shownin FIG. 1A, the gNB 115-1 and the gNB 115-2 may be connected to the eNB110. Alternatively, the gNB 115-1 and the gNB 115-2 may be connected todifferent eNBs.

The load management system 125 may include one or more devices that areconfigured to balance a load of a gNB 115 to reduce the load of the gNB115, as explained in more detail below. In some implementations, theload of the gNB 115 may include a processing load of the gNB 115.Additionally, or alternatively, the load of the gNB 115 may include aradio frequency (RF) load of the gNB 115, a backhaul load of the gNB115, among other examples. For example, the load management system 125may determine the load of the gNB 115. Based on the load of the gNB 115,the load management system 125 may cause one or more network repeatersto be disconnected from the gNB 115 in order to prevent the load of thegNB 115 from reaching a maximum load of the gNB 115. In someimplementations, the load management system 125 may be included in a gNB115. Additionally, or alternatively, the load management system 125 maybe included in a device that is part of a cloud computing environment.Additionally, or alternatively, the load management system 125 may beincluded in a multi-access edge computing (MEC) device. In someexamples, the load management system 125 may be implemented as aself-optimizing network.

The base station data structure 130 may include a data structure (e.g.,a database, a table, a list, and/or the like) that stores informationregarding one or more eNBs (e.g., the eNB 110) and/or regarding one ormore gNBs (e.g., the gNB 115-1, the gNB 115-2, among other examples).For example, the base station data structure 130 may store configurationinformation of the one or more eNBs and/or of the one or more gNBs. Insome implementations, the configuration information of a gNB 115 mayinclude information identifying the gNB 115, information identifyingdevices connected to the gNB 115, and/or load information indicating aload of the gNB 115 (e.g., a load associated with the devices connectedto the gNB 115). In some examples, the devices connected to the gNB 115may include one or more network repeaters (e.g., network repeater 105).

In some situations, the configuration information may be provided to thebase station data structure 130 for storage by the gNB 115.Additionally, or alternatively, the configuration information may beprovided to the base station data structure 130 for storage by thedevices connected to the gNB 115. Additionally, or alternatively, theconfiguration information may be provided to the base station datastructure 130 by one or more devices of a network associated with thegNB 115. In some implementations, the configuration information may beprovided using an application program interface (API) (e.g., arepresentational state transfer (REST) API).

The network repeater data structure 135 may include a data structure(e.g., a database, a table, a list, and/or the like) that storesinformation regarding one or more network repeaters. The one or morenetwork repeaters may include the network repeater 105. In somesituations, the information regarding the one or more network repeatersmay be provided by the one or more network repeaters. Additionally, oralternatively, the information regarding the one or more networkrepeaters may be provided by one or more devices of a network associatedwith the one or more network repeaters.

In some implementations, the information regarding the one or morenetwork repeaters may be provided using an API (e.g., a REST API). Insome situations, the information regarding the gNB 115-2 may be providedvia 4G connectivity.

In some implementations, the network repeater data structure 135 mayinclude information identifying the one or more network repeaters andconnectivity information of the one or more network repeaters. Theconnectivity information may be stored in association with theinformation identifying the one or more network repeaters. In someexamples, the connectivity information of the network repeater 105 mayinclude information identifying a quantity of devices connected to thenetwork repeater 105, information regarding an amount of data exchangedwith the devices connected to the network repeater 105, base stationinformation identifying one or more base stations (e.g., one or moregNBs 115) to which the network repeater may connect, beam informationidentifying one or more beam indexes associated with the one or morebase stations, and/or signal information regarding one or more signalstransmitted by the one or more base stations.

In the example described herein, the one or more base stations mayinclude the gNB 115-1 and/or the gNB 115-2. The signal information mayindicate a measure of signal strength and/or a measure of signal qualityof the one or more signals. In some implementations, the networkrepeater 105 may generate the connectivity information duringcommissioning (or deployment) of the network repeater 105 and providethe connectivity information to the network repeater data structure 135for storage. For example, during the commissioning (or deployment), thenetwork repeater 105 may identify the one or more base stations (e.g.,identify one or more base stations within a distance threshold of thenetwork repeater 105).

The network repeater 105 may determine the signal information regardingthe one or more signals transmitted by the one or more base stations(e.g., one or more mmWave communication signals). For example, thenetwork repeater 105 may determine a reference signal received power(RSRP) of a signal received from the gNB 115-1, a signal to interferenceand noise ratio (SINR) of the signal received from the gNB 115-1 andreceived by the network repeater 105, among other examples. The networkrepeater 105 may perform similar actions with respect to a signaltransmitted by the gNB 115-2.

In some situations, the network repeater 105 may rank the one or morebase stations based on the signal information. For example, the gNB115-1 may be ranked higher than the gNB 115-2 if the measure of signalstrength of the signal received from the gNB 115-1 exceeds the measureof signal strength of a signal received from the gNB 115-2.Additionally, or alternatively, the gNB 115-1 may be ranked higher thanthe gNB 115-2 if the measure of signal quality of the signal receivedfrom the gNB 115-1 exceeds the measure of signal quality of the signalreceived from the gNB 115-2.

In some examples, the connectivity information may include informationidentifying a ranking of the one or more base stations based on thesignal information. The information identifying the quantity of devicesconnected to the network repeater 105 may include informationidentifying a quantity of devices currently connected to the networkrepeater 105 during the commissioning (or deployment) of the networkrepeater 105.

In some implementations, after the commissioning (or deployment) ofnetwork repeater 105, the network repeater 105 may update theconnectivity information and provide the updated connectivityinformation to the network repeater data structure 135 for storage. Forexample, the network repeater 105 may update the connectivityinformation periodically (e.g., every ten minutes, every thirty minutes,among other examples). Additionally, or alternatively, the networkrepeater 105 may update the connectivity information based on a trigger(e.g., based on a request from the load management system 125, based ona request from the one or more base stations, among other examples).

In the example that follows, the network repeater 105 may be connectedto the gNB 115-1. In this regard, the devices 120 connected to thenetwork repeater 105 may be connected to the gNB 115-1 via the networkrepeater 105. The network repeater 105 may be capable of connecting toone or more other base stations, such as the gNB 115-2.

As shown in FIG. 1A, and by reference number 140, the load managementsystem 125 may determine a load of a first base station. In the exampledescribed herein, the first base station may be the gNB 115-1. In someimplementations, the load management system 125 may obtain loadinformation indicating the load of the gNB 115-1 and determine the loadbased on the load information. In some situations, the load managementsystem 125 may obtain the load information from one or more memoriesassociated with the gNB 115-1.

In some examples, the load information may include informationidentifying a quantity of devices connected to the gNB 115-1.Additionally, or alternatively, the load information may includeinformation identifying an amount of data exchanged between the gNB115-1 and the devices connected to the gNB 115-1. In this regard, theload management system 125 may determine the load of the gNB 115-1 basedon the quantity of devices and/or based on the amount of data.

The load management system 125 may determine the load periodically(e.g., every minute, every ten minutes, every thirty minutes, amongother examples). Additionally, or alternatively, the load managementsystem 125 may determine the load based on a trigger (e.g., based on arequest from one or more devices of the network associated with the gNB115-1, based on determining the load of another base station, amongother examples).

As shown in FIG. 1A, and by reference number 145, the load managementsystem 125 may determine that the load satisfies a first load thresholdthat is less than a second load threshold. The second load threshold mayindicate a maximum load of the gNB 115-1.

The first load threshold may be a device quantity threshold of devicesconnected to the gNB 115-1. Additionally, or alternatively, the firstload threshold may be a data quantity threshold regarding an amount ofdata exchanged with devices connected to the gNB 115-1. The second loadthreshold may be a maximum quantity of devices that may be connected tothe gNB 115-1. Additionally, or alternatively, the second load thresholdmay be a maximum amount of data to be exchanged with devices that may beconnected to the gNB 115-1.

The load management system 125 may compare the load of the gNB 115-1 andthe first load threshold. Based on comparing the load of the gNB 115-1and the first load threshold, the load management system 125 maydetermine that the load of the gNB 115-1 satisfies the first loadthreshold. For example, the load management system 125 may determinethat the quantity of devices connected to the gNB 115-1 satisfies thedevice quantity threshold. Additionally, or alternatively, the loadmanagement system 125 may determine that the amount of data (exchangedbetween the gNB 115-1 and the devices connected to the gNB 115-1)satisfies the data quantity threshold.

As shown in FIG. 1B, and by reference number 150, the load managementsystem 125 may obtain configuration information of the first basestation. For example, based on determining that the load satisfies thefirst load threshold, the load management system 125 may obtain theconfiguration information of the gNB 115-1 from the base station datastructure 130. In some implementations, the load management system 125may perform a lookup of the base station data structure 130 and obtainthe configuration information of the gNB 115-1 from the base stationdata structure 130 based on the lookup. The lookup may be performedusing information identifying the gNB 115-1, such as a physical cellidentifier associated with the gNB 115-1. In the base station datastructure 130, the configuration information of the gNB 115-1 may beassociated with the information identifying the gNB 115-1. Theconfiguration information of the gNB 115-1 may include informationidentifying the devices connected to the gNB 115-1.

As shown in FIG. 1B, and by reference number 155, the load managementsystem 125 may determine that the first base station is connected to anetwork repeater. In the example described herein, the network repeatermay be the network repeater 105. In some implementations, the loadmanagement system 125 may analyze the configuration of the gNB 115-1 anddetermine that the configuration information includes informationidentifying the network repeater 105. For example, the devices mayinclude the network repeater 105, and the information identifying thedevices may include the information identifying the network repeater105.

In some examples, the load management system 125 may determine that theinformation identifying the network repeater 105 identifies a networkrepeater (e.g., based on a format of the information identifying thenetwork repeater 105, based on content of the information identifyingthe network repeater 105, among other examples). The informationidentifying the network repeater 105 may include an international mobileequipment identity (IMEI), a mobile directory number (MDN), a serviceset identifier (SSID), among other examples.

In some situations, the gNB 115-1 may be connected to multiple networkrepeaters. In this regard, based on analyzing the configurationinformation, the load management system 125 may determine that theconfiguration information includes information identifying one or moreadditional network repeaters in a manner similar to the manner describedabove.

As shown in FIG. 1C, and by reference number 160, the load managementsystem 125 may obtain connectivity information of the network repeater.For example, the load management system 125 may receive the connectivityinformation of the network repeater 105 from the network repeater datastructure 135. In some implementations, based on determining that thegNB 115-1 is connected to the network repeater 105, the load managementsystem 125 may perform a lookup of the network repeater data structure135 and may obtain the connectivity information of the network repeater105 from the network repeater data structure 135 based on the lookup.The lookup may be performed using the information identifying thenetwork repeater 105.

The connectivity information of the network repeater 105 has beendescribed above. In some examples, the information (included in theconnectivity information) identifying the ranking of the one or morebase stations may identify the gNB 115-1 as a primary base station forthe network repeater 105, identify the gNB 115-2 as a secondary basestation for the network repeater 105, information identifying a thirdbase station (e.g., a third gNB 115) as a tertiary base station, and soon. The load management system 125 may attempt to cause the networkrepeater 105 to connect to the one or more base stations in an orderthat is based on the ranking of the one or more base stations.

As shown in FIG. 1C, and by reference number 165, the load managementsystem 125 may determine that the network repeater is capable ofconnecting to a second base station. In the example described herein,the second base station may be the gNB 115-2. In some implementations,the load management system 125 may determine that the network repeater105 is capable of connecting to the gNB 115-2 based on the connectivityinformation. For example, the load management system 125 may determinethat the network repeater 105 is capable of connecting to the gNB 115-2based on the connectivity information including the informationidentifying the gNB 115-2. In some situations, the load managementsystem 125 may determine that the network repeater 105 is capable ofconnecting to one or more additional base stations in a similar manner.

As shown in FIG. 1D, and by reference number 170, the load managementsystem 125 may determine a load associated with devices connected to thenetwork repeater. The load may be referred to as the load of the networkrepeater 105. In some implementations, the load management system 125may determine the load of the network repeater 105 based on theconnectivity information. For example, the load management system 125may determine the quantity of devices connected to the network repeater105 based on the information identifying the quantity of devicesconnected to the network repeater 105. Additionally, or alternatively,the load management system 125 may determine the amount of data based onthe information regarding the amount of data exchanged with the devicesconnected to the network repeater 105. The load management system 125may determine the load of the network repeater 105 based on the quantityof devices connected to the network repeater 105 and/or based on theamount of data exchanged with the devices connected to the networkrepeater 105 in a manner similar to the manner described above inconnection with the load of the gNB 115-1.

In some implementations, the load management system 125 may predict theload of the network repeater 105 based on historical data regarding theload of the network repeater 105. In this regard, the load managementsystem 125 may implement a machine learning model that is trained, basedon the historical data, to predict the load of the network repeater 105.In some examples, the load management system 125 may obtain thehistorical data from the network repeater data structure 135. Thenetwork repeater data structure 135 may accumulate the historical dataover a period of time. The historical data may identify historical loadsof the network repeater 105, historical quantities of devices connectedto the network repeater 105, historical amounts of data exchangedbetween the network repeater 105 and devices connected to the networkrepeater 105, among other examples. The load management system 125 maypredict the load of the network repeater 105 using the historical dataand one or more mathematical algorithms or operations.

For example, the load management system 125 may determine a minimum loadof the historical data and predict the load based on the minimum load.Additionally, or alternatively, the load management system 125 maydetermine a maximum load of the historical data and predict the loadbased on the maximum load. Additionally, or alternatively, the loadmanagement system 125 may determine an average load of the historicaldata and predict the load based on the average load.

The load management system 125 may perform similar actions for one ormore additional network repeaters connected to the gNB 115-1 todetermine the load of the one or more additional network repeaters. Insome situations, the load management system 125 may compare the load ofthe network repeater 105 and the load of the one or more additionalnetwork repeaters to identify a network repeater that is to bedisconnected from the gNB 115-1 to reduce the load of the gNB 115-1. Insome examples, the load management system 125 may identify a networkrepeater associated with a load that exceeds the load of all networkrepeaters connected to the gNB 115-1. For instance, the load managementsystem 125 may determine that the load of the network repeater 105exceeds the load of all network repeaters connected to the gNB 115-1

The load management system 125 may determine that the load of thenetwork repeater 105 causes the load of the gNB 115-1 to satisfy thefirst threshold load. For example, the load management system 125 maydetermine that the quantity of devices connected to the network repeater105 and/or the amount of data (exchanged between the network repeater105 and the devices connected to the network repeater 105) cause theload of the gNB 115-1 to satisfy the first load threshold. Based ondetermining that the load of the network repeater 105 causes the load ofthe gNB 115-1 to satisfy the first load threshold, the load managementsystem 125 may determine that the network repeater 105 is to bedisconnected from the gNB 115-1 and connected to another base station(e.g., the gNB 115-2) to prevent the load of the gNB 115-1 fromsatisfying the second threshold. In this regard, the load managementsystem 125 may determine whether the gNB 115-2 can establish aconnection with the network repeater 105.

In some situations, the load management system 125 may determine thatmultiple network repeaters are to be disconnected from the gNB 115-1. Inthis regard, the load management system 125 may identify one or morebase stations identified by the connectivity information of the multiplenetwork repeaters and determine whether the one or more base stationscan establish a connection with the multiple network repeaters asdescribed herein.

As shown in FIG. 1D, and by reference number 175, the load managementsystem 125 may determine a load of a second base station. In the exampledescribed herein, the second base station may be the gNB 115-2. In someimplementations, the load management system 125 may determine whetherthe gNB 115-2 can establish the connection with the network repeater 105based on the load of the gNB 115-2. The load management system 125 maydetermine the load of the gNB 115-2 in a manner similar to the mannerdescribed above in connection with determining the load of the gNB115-1.

After determining the load of the gNB 115-2, the load management system125 may determine whether the load of the gNB 115-2 satisfies a thirdload threshold that is less than a fourth load threshold. The fourthload threshold may indicate a maximum load of the gNB 115-2. In someimplementations, the third load threshold may be similar to the firstload threshold and/or the third load threshold may be similar to thefirst load threshold. Alternatively, the third load threshold may bedifferent than the first load threshold and/or the third load thresholdmay be different than the first load threshold.

If the load management system 125 determines that the load of the gNB115-2 satisfies the third load threshold, the load management system 125may determine whether a next base station (identified in theconnectivity information of the network repeater 105) can establish aconnection with the network repeater 105 based on a load of the nextbase station, in a manner similar to the manner described in connectionwith the gNB 115-2.

As shown in FIG. 1E, and by reference number 180, the load managementsystem 125 may cause the network repeater to connect to the second basestation. For example, the load management system 125 may determine thatthe load of the gNB 115-2 does not satisfy the third load threshold.Based on determining that the load of the gNB 115-2 does not satisfy thethird load threshold, the load management system 125 may determinewhether the load of the network repeater 105 will cause the load of thegNB 115-2 to satisfy the third load threshold. In other words, the loadmanagement system 125 may determine whether causing the network repeater105 to connect to the gNB 115-2 will cause the load of the gNB 115-2 tosatisfy the third load threshold. If the network repeater 105 determinesthat the load of the network repeater 105 will cause the load of the gNB115-2 to satisfy the third load threshold, the load management system125 may determine whether a next base station (identified in theconnectivity information of the network repeater 105) can establish aconnection with the network repeater 105.

Based on determining that the load of the network repeater 105 will notcause the load of the gNB 115-2 to satisfy the third load threshold, thenetwork repeater 105 may cause the network repeater 105 to connect tothe gNB 115-2 to reduce the load of the gNB 115-1. In other words, theload management system 125 may cause the network repeater 105 to connectto the gNB 115-2 based on the load of the gNB 115-1 satisfying the firstload threshold, the load of the network repeater 105, the networkrepeater 105 being capable of connecting to the gNB 115-2, and the loadof the gNB 115-2. Accordingly, based on determining that the load of thegNB 115-1 satisfies the first load threshold, the load management system125 may cause the network repeater 105 to connect to the gNB 115-2 inorder to prevent the load of the gNB 115-1 from satisfying the secondload threshold. The gNB 115-1 may be configured to disconnect from oneor more of the devices connected to the gNB 115-1 when the load of thegNB 115-1 satisfies the second load threshold.

In some implementations, the load management system 125 may cause thenetwork repeater 105 to perform a handover operation to cause thenetwork repeater 105 to connect to the gNB 115-2. The load managementsystem 125 may cause information regarding the gNB 115-2 to be providedto the network repeater 105 to cause the network repeater 105 to connectto the gNB 115-2. The information regarding the network repeater 105 mayinclude a physical cell identifier associated with the gNB 115-2 and abeam index associated with the gNB 115-2. In some examples, theinformation regarding the gNB 115-2 may allow the network repeater 105to be automatically beam aligned and configured for attaching to the gNB115-2.

In some examples, the information regarding the gNB 115-2 may furtherinclude master information block (MIB) data associated with the gNB115-2, system information blocks (SIB) associated with the gNB 115-2, anabsolute radio frequency (RF) channel number associated with the gNB115-2, a band of operation (e.g., n260, n261, among other examples)associated with the gNB 115-2, time division duplex timing informationassociated with the gNB 115-2, periodicity, uplink symbols, downlinksymbols, uplink slots, downlink slots, a slot format indicator,subcarrier offsets associated with the gNB 115-2, subcarrier spacingsassociated with the gNB 115-2, a physical cell identifier associatedwith the gNB 115-2, among other examples.

The information regarding the gNB 115-2 may further include informationthat causes the network repeater 105 to connect to the gNB 115-1 duringa period of time between a downlink communication associated with thegNB 115-1 and an uplink communication associated with the gNB 115-1. Insome implementations, the information regarding the gNB 115-2 may beprovided via 4G connectivity.

After causing the network repeater 105 to connect to the gNB 115-2, theload management system 125 may cause the load information of the gNB115-1 to be updated to indicate an updated load of the gNB 115-1. Insome implementations, the load information may be updated using an API(e.g., a REST API). The load management system 125 may cause loadinformation of the gNB 115-2 to be updated in a similar manner.

In some situations, after a period of time following the networkrepeater 105 connecting to the gNB 115-2, the load management system 125may determine whether the network repeater 105 is to be reconnected tothe gNB 115-1. For example, the load management system 125 may performactions similar to the actions described above to determine whether thenetwork repeater 105 is to be reconnected to the gNB 115-1 and to causethe network repeater 105 to be connected to the gNB 115-1 accordingly.

By causing the network repeater 105 to connect to the gNB 115-2 in thismanner, the implementations described herein may prevent the load of thegNB 115-1 from reaching the maximum load and, accordingly, prevent thegNB 115-1 from being overloaded. As a result of preventing the gNB 115-1from being overloaded, the implementations described herein may preventthe gNB 115-1 from disconnecting from one or more devices. By preventingthe gNB 115-1 from disconnecting from the one or more devices, theimplementations described herein may prevent poor network performance.Additionally, by preventing the gNB 115-1 from disconnecting from theone or more devices, the implementations described herein may preservenetwork resources, computing resources, and/or other resources thatwould been otherwise consumed in order to re-establish a connection withthe gNB 115-1.

As indicated above, FIGS. 1A-1E are provided as an example. Otherexamples may differ from what is described with regard to FIGS. 1A-1E.The number and arrangement of devices shown in FIGS. 1A-1E are providedas an example. In practice, there may be additional devices, fewerdevices, different devices, or differently arranged devices than thoseshown in FIGS. 1A-1E. Furthermore, two or more devices shown in FIGS.1A-1E may be implemented within a single device, or a single deviceshown in FIGS. 1A-1E may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) shown in FIGS. 1A-1E may perform one or more functionsdescribed as being performed by another set of devices shown in FIGS.1A-1E.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2 ,environment 200 may include a load management system 201, which mayinclude one or more elements of and/or may execute within a cloudcomputing system 202. The cloud computing system 202 may include one ormore elements 203-213, as described in more detail below. As furthershown in FIG. 2 , environment 200 may include a network 220, the eNB110, the gNB 115-1, the gNB 115-2, the base station data structure 130,and/or the network repeater data structure 135. Devices and/or elementsof environment 200 may interconnect via wired connections and/orwireless connections.

The cloud computing system 202 includes computing hardware 203, aresource management component 204, a host operating system (OS) 205,and/or one or more virtual computing systems 206. The cloud computingsystem 202 may execute on, for example, an Amazon Web Services platform,a Microsoft Azure platform, or a Snowflake platform. The resourcemanagement component 204 may perform virtualization (e.g., abstraction)of computing hardware 203 to create the one or more virtual computingsystems 206. Using virtualization, the resource management component 204enables a single computing device (e.g., a computer or a server) tooperate like multiple computing devices, such as by creating multipleisolated virtual computing systems 206 from computing hardware 203 ofthe single computing device. In this way, computing hardware 203 canoperate more efficiently, with lower power consumption, higherreliability, higher availability, higher utilization, greaterflexibility, and lower cost than using separate computing devices.

Computing hardware 203 includes hardware and corresponding resourcesfrom one or more computing devices. For example, computing hardware 203may include hardware from a single computing device (e.g., a singleserver) or from multiple computing devices (e.g., multiple servers),such as multiple computing devices in one or more data centers. Asshown, computing hardware 203 may include one or more processors 207,one or more memories 208, one or more storage components 209, and/or oneor more networking components 210. Examples of a processor, a memory, astorage component, and a networking component (e.g., a communicationcomponent) are described elsewhere herein.

The resource management component 204 includes a virtualizationapplication (e.g., executing on hardware, such as computing hardware203) capable of virtualizing computing hardware 203 to start, stop,and/or manage one or more virtual computing systems 206. For example,the resource management component 204 may include a hypervisor (e.g., abare-metal or Type 1 hypervisor, a hosted or Type 2 hypervisor, oranother type of hypervisor) or a virtual machine monitor, such as whenthe virtual computing systems 206 are virtual machines 211.Additionally, or alternatively, the resource management component 204may include a container manager, such as when the virtual computingsystems 206 are containers 212. In some implementations, the resourcemanagement component 204 executes within and/or in coordination with ahost operating system 205.

A virtual computing system 206 includes a virtual environment thatenables cloud-based execution of operations and/or processes describedherein using computing hardware 203. As shown, a virtual computingsystem 206 may include a virtual machine 211, a container 212, or ahybrid environment 213 that includes a virtual machine and a container,among other examples. A virtual computing system 206 may execute one ormore applications using a file system that includes binary files,software libraries, and/or other resources required to executeapplications on a guest operating system (e.g., within the virtualcomputing system 206) or the host operating system 205.

Although the load management system 201 may include one or more elements203-213 of the cloud computing system 202, may execute within the cloudcomputing system 202, and/or may be hosted within the cloud computingsystem 202, in some implementations, the load management system 201 maynot be cloud-based (e.g., may be implemented outside of a cloudcomputing system) or may be partially cloud-based. For example, the loadmanagement system 201 may include one or more devices that are not partof the cloud computing system 202, such as device 300 of FIG. 3 , whichmay include a standalone server or another type of computing device. Theload management system 201 may perform one or more operations and/orprocesses described in more detail elsewhere herein.

Network 220 includes one or more wired and/or wireless networks. Forexample, network 220 may include a cellular network, a public landmobile network (PLMN), a local area network (LAN), a wide area network(WAN), a private network, the Internet, and/or a combination of these orother types of networks. The network 220 enables communication among thedevices of environment 200.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2 . Furthermore, two or more devices shown in FIG. 2 maybe implemented within a single device, or a single device shown in FIG.2 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300, which maycorrespond to the network repeater 105, the eNB 110, the gNB 115-1,and/or the gNB 115-2. In some implementations, the network repeater 105,the eNB 110, the gNB 115-1, and/or the gNB 115-2 may include one or moredevices 300 and/or one or more components of device 300. As shown inFIG. 3 , device 300 may include a bus 310, a processor 320, a memory330, a storage component 340, an input component 350, an outputcomponent 360, and a communication component 370.

Bus 310 includes a component that enables wired and/or wirelesscommunication among the components of device 300. Processor 320 includesa central processing unit, a graphics processing unit, a microprocessor,a controller, a microcontroller, a digital signal processor, afield-programmable gate array, an application-specific integratedcircuit, and/or another type of processing component. Processor 320 isimplemented in hardware, firmware, or a combination of hardware andsoftware. In some implementations, processor 320 includes one or moreprocessors capable of being programmed to perform a function. Memory 330includes a random access memory, a read only memory, and/or another typeof memory (e.g., a flash memory, a magnetic memory, and/or an opticalmemory).

Storage component 340 stores information and/or software related to theoperation of device 300. For example, storage component 340 may includea hard disk drive, a magnetic disk drive, an optical disk drive, a solidstate disk drive, a compact disc, a digital versatile disc, and/oranother type of non-transitory computer-readable medium. Input component350 enables device 300 to receive input, such as user input and/orsensed inputs. For example, input component 350 may include a touchscreen, a keyboard, a keypad, a mouse, a button, a microphone, a switch,a sensor, a global positioning system component, an accelerometer, agyroscope, and/or an actuator. Output component 360 enables device 300to provide output, such as via a display, a speaker, and/or one or morelight-emitting diodes. Communication component 370 enables device 300 tocommunicate with other devices, such as via a wired connection and/or awireless connection. For example, communication component 370 mayinclude a receiver, a transmitter, a transceiver, a modem, a networkinterface card, and/or an antenna.

Device 300 may perform one or more processes described herein. Forexample, a non-transitory computer-readable medium (e.g., memory 330and/or storage component 340) may store a set of instructions (e.g., oneor more instructions, code, software code, and/or program code) forexecution by processor 320. Processor 320 may execute the set ofinstructions to perform one or more processes described herein. In someimplementations, execution of the set of instructions, by one or moreprocessors 320, causes the one or more processors 320 and/or the device300 to perform one or more processes described herein. In someimplementations, hardwired circuitry may be used instead of or incombination with the instructions to perform one or more processesdescribed herein. Thus, implementations described herein are not limitedto any specific combination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 3 are provided asan example. Device 300 may include additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 3 . Additionally, or alternatively, a set ofcomponents (e.g., one or more components) of device 300 may perform oneor more functions described as being performed by another set ofcomponents of device 300.

FIG. 4 is a flowchart of an example process 400 associated with systemsand methods for load balancing devices. In some implementations, one ormore process blocks of FIG. 4 may be performed by a device (e.g., theload management system 125). In some implementations, one or moreprocess blocks of FIG. 4 may be performed by another device or a groupof devices separate from or including the device, such as a the networkrepeater 105 (e.g., the network repeater 105 r), a eNB (e.g., the eNB110), and/or a gNB (e.g., the gNB 115-1 and/or the gNB 115-2).Additionally, or alternatively, one or more process blocks of FIG. 4 maybe performed by one or more components of device 300, such as processor320, memory 330, storage component 340, input component 350, outputcomponent 360, and/or communication component 370.

As shown in FIG. 4 , process 400 may include obtaining load informationindicating a load of a first base station (block 410). For example, thedevice may obtain load information indicating a load of a first basestation, wherein the load is associated with devices connected to thefirst base station, as described above. In some implementations, theload is associated with devices connected to the first base station.

As further shown in FIG. 4 , process 400 may include determining thatthe load satisfies a load threshold of the first base station (block420). For example, the device may determine that the load satisfies aload threshold of the first base station, as described above.

As further shown in FIG. 4 , process 400 may include determining that anetwork repeater is connected to the first base station (block 430). Forexample, the device may determine that a network repeater is connectedto the first base station, as described above.

In some implementations, determining that the network repeater isconnected to the first base station comprises obtaining configurationinformation of the first base station, wherein the configurationinformation includes information identifying the devices connected tothe first base station, and determining, based on the configurationinformation, that the devices include the network repeater.

As further shown in FIG. 4 , process 400 may include determining that aplurality of devices are connected to the network repeater (block 440).For example, the device may determine that a plurality of devices areconnected to the network repeater, as described above.

As further shown in FIG. 4 , process 400 may include determining thatthe network repeater is capable of connecting to a second base station(block 450). For example, the device may determine that the networkrepeater is capable of connecting to a second base station, as describedabove.

In some implementations, determining that the network repeater iscapable of connecting to the second base station comprises obtainingconnectivity information of the network repeater, wherein theconnectivity information includes first information identifying thefirst base station as a primary base station for the network repeaterand second information identifying the second base station as asecondary base station for the network repeater, and determining thatthe network repeater is capable of connecting to the second base stationbased on the connectivity information.

As further shown in FIG. 4 , process 400 may include causing the networkrepeater to connect to the second base station to reduce the load basedon: (block 460). For example, the device may cause the network repeaterto connect to the second base station to reduce the load based on: theload satisfying the load threshold, the plurality of devices beingconnected to the network repeater, and the network repeater beingcapable of connecting to the second base station, as described above.

In some implementations, causing the network repeater to connect to thesecond base station comprises causing the network repeater to connect tothe second base station during a period of time between a downlinkcommunication associated with the first base station and an uplinkcommunication associated with the first base station.

In some implementations, process 400 includes receiving informationindicating that the network repeater has connected to the second basestation, and updating the load information to indicate an updated loadof the first base station, after causing the network repeater to connectto the second base station.

In some implementations, the load of the first base station is a firstload, and wherein causing the network repeater to connect to the secondbase station comprises determining a second load of the second basestation, determining a load associated with devices connected to thenetwork repeater, and causing the network repeater to connect to thesecond base station based on the second load of the second base stationand the load associated with the devices.

In some implementations, the load threshold is a first load threshold,and wherein causing the network repeater to connect to the second basestation comprises determining that the load, associated with thedevices, does not cause the second load to satisfy a second loadthreshold of the second base station, and causing the network repeaterto connect to the second base station based on determining that theload, associated with the quantity of devices, does not cause the secondload to satisfy the second load threshold.

In some implementations, the network repeater is a first networkrepeater, the quantity of devices, connected to the first networkrepeater, is a first quantity of devices, and causing the networkrepeater to connect to the second base station comprises determiningthat a second network repeater is connected to the first base station;determining a second quantity of devices connected to the second networkrepeater; and determining whether to cause the first network repeater toconnect to the second base station or cause the second network repeaterto connect to the second base station based on a first total loadassociated with the first quantity of devices and a second total loadassociated with the second quantity of devices.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4 . Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Itwill be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set. As used herein, aphrase referring to “at least one of” a list of items refers to anycombination of those items, including single members. As an example, “atleast one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c,and a-b-c, as well as any combination with multiple of the same item.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, or a combination of related and unrelateditems), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”). In the precedingspecification, various example embodiments have been described withreference to the accompanying drawings. It will, however, be evidentthat various modifications and changes may be made thereto, andadditional embodiments may be implemented, without departing from thebroader scope of the invention as set forth in the claims that follow.The specification and drawings are accordingly to be regarded in anillustrative rather than restrictive sense.

What is claimed is:
 1. A method performed by a device, the methodcomprising: obtaining load information indicating a load of a first basestation, wherein the load is associated with devices connected to thefirst base station; determining that the load satisfies a load thresholdof the first base station; determining that a network repeater isconnected to the first base station; determining that a plurality ofdevices are connected to the network repeater; determining that thenetwork repeater is capable of connecting to a second base station; andcausing the network repeater to connect to the second base station toreduce the load based on: the load satisfying the load threshold, theplurality of devices being connected to the network repeater, and thenetwork repeater being capable of connecting to the second base station.2. The method of claim 1, wherein causing the network repeater toconnect to the second base station comprises: determining that thenetwork repeater is capable of being connected to a third base station;determining that a first measure of signal quality, of the second basestation, exceeds a second measure of signal quality of the third basestation; and causing the network repeater to connect to the second basestation based on determining that the first measure of signal qualityexceeds the second measure of signal quality
 3. The method of claim 1,further comprising: receiving information indicating that the networkrepeater has connected to the second base station; and updating the loadinformation to indicate an updated load of the first base station, aftercausing the network repeater to connect to the second base station. 4.The method of claim 1, wherein determining that the network repeater isconnected to the first base station comprises: obtaining configurationinformation of the first base station, wherein the configurationinformation includes information identifying the devices connected tothe first base station; and determining, based on the configurationinformation, that the devices include the network repeater.
 5. Themethod of claim 1, wherein determining that the network repeater iscapable of connecting to the second base station comprises: obtainingconnectivity information of the network repeater, wherein theconnectivity information includes first information identifying thefirst base station as a primary base station for the network repeaterand second information identifying the second base station as asecondary base station for the network repeater; and determining thatthe network repeater is capable of connecting to the second base stationbased on the connectivity information.
 6. The method of claim 1, wherethe load of the first base station is a first load, and wherein causingthe network repeater to connect to the second base station comprises:determining a second load of the second base station; determining a loadassociated with devices connected to the network repeater; and causingthe network repeater to connect to the second base station based on thesecond load of the second base station and the load associated with thedevices.
 7. The method of claim 6, wherein the load threshold is a firstload threshold, and wherein causing the network repeater to connect tothe second base station comprises: determining that the load, associatedwith the devices, does not cause the second load to satisfy a secondload threshold of the second base station; and causing the networkrepeater to connect to the second base station based on determining thatthe load, associated with the devices, does not cause the second load tosatisfy the second load threshold.
 8. A device, comprising: one or moreprocessors configured to: determine that a load, of a first basestation, satisfies a load threshold; determine whether a networkrepeater is connected to the first base station, wherein a plurality ofdevices are connected to the network repeater; determine whether thenetwork repeater is capable of being connected to a second base stationbased on determining that the first base station is connected to thenetwork repeater; determine a quantity of devices connected to thenetwork repeater; and cause the network repeater to connect to thesecond base station to reduce the load based on: the load satisfying theload threshold, determining that the network repeater is capable ofbeing connected to the second base station, and the quantity of devices.9. The device of claim 8, wherein the plurality of devices is a firstplurality of devices, wherein the load threshold is a first loadthreshold, wherein the first base station is connected to a secondplurality of devices, and wherein the one or more processors, to causethe network repeater to connect to the second base station, areconfigured to: cause the network repeater to connect to the second basestation to reduce the load to prevent the load from satisfying a secondload threshold that exceeds the first load threshold, wherein the firstbase station is configured to disconnect from one or more of the secondplurality of devices when the load satisfies the second load threshold.10. The device of claim 8, wherein the one or more processors, to causethe network repeater to connect to the second base station, areconfigured to: determine that the quantity of devices causes the load tosatisfy the load threshold; and cause the network repeater to connect tothe second base station based on determining that the quantity ofdevices causes the load to satisfy the load threshold.
 11. The device ofclaim 8, wherein the one or more processors are further configured to:determine that the network repeater is capable of being connected to athird base station; determine that a first measure of signal quality, ofthe second base station, exceeds a second measure of signal quality ofthe third base station; and cause the network repeater to connect to thesecond base station based on determining that the first measure ofsignal quality exceeds the second measure of signal quality.
 12. Thedevice of claim 8, wherein the network repeater is a first networkrepeater, wherein the quantity of devices, connected to the firstnetwork repeater, is a first quantity of devices, and wherein the one ormore processors, to cause the network repeater to connect to the secondbase station, are configured to: determine that a second networkrepeater is connected to the first base station; determine a secondquantity of devices connected to the second network repeater; anddetermine whether to cause the first network repeater to connect to thesecond base station or cause the second network repeater to connect tothe second base station based on a first total load associated with thefirst quantity of devices and a second total load associated with thesecond quantity of devices.
 13. The device of claim 12, wherein the oneor more processors, to cause the network repeater to connect to thesecond base station, are configured to: determine that the first totalload exceeds the second total load; and cause the first network repeaterto connect to the second base station based on determining that thefirst total load exceeds the second total load.
 14. The device of claim8, wherein the one or more processors, to cause the network repeater toconnect to the second base station, are configured to: cause informationregarding the second base station to be provided to the networkrepeater, wherein the information regarding the first base stationincludes a physical cell identifier associated with the second basestation and a beam index associated with the second base station.
 15. Anon-transitory computer-readable medium storing a set of instructions,the set of instructions comprising: one or more instructions that, whenexecuted by one or more processors of a device, cause the device to:determine that a first load, of a first base station, satisfies a loadthreshold; determine that a network repeater is connected to the firstbase station; determine a second load associated with devices connectedto the network repeater; and cause the network repeater to connect to asecond base station to reduce the first load based on the second load.16. The non-transitory computer-readable medium of claim 15, wherein theone or more instructions, when executed by the one or more processors,further cause the device to: determine that the network repeater iscapable of being connected to the second base station; and cause thenetwork repeater to connect to the second base station further based ondetermining that the network repeater is capable of being connected tothe second base station.
 17. The non-transitory computer-readable mediumof claim 15, wherein the one or more instructions, that cause the deviceto cause the network repeater to connect to the second base station,cause the device to: cause information regarding the second base stationto be provided to the network repeater, wherein the informationregarding the first base station includes information identifying thesecond base station and information identifying a beam associated withthe second base station.
 18. The non-transitory computer-readable mediumof claim 15, wherein the network repeater is a first network repeater,and wherein the one or more instructions, when executed by the one ormore processors, further cause the device to: determine that the firstload does not satisfy the load threshold after causing the networkrepeater to connect to the second base station; determine a third loadassociated with devices connected to a second network repeater; andcause the second network repeater to be connected to the first basestation based on determining that the first load does not satisfy theload threshold and based on the third load.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, when executed by the one or more processors, further causethe device to: determine that the network repeater is capable of beingconnected to a third base station; determine that a first measure ofsignal quality, of the second base station, exceeds a second measure ofsignal quality of the third base station; and cause the network repeaterto connect to the second base station based on determining that thefirst measure of signal quality exceeds the second measure of signalquality.
 20. The non-transitory computer-readable medium of claim 15,wherein the load threshold is a first load threshold, wherein the firstbase station is connected to a plurality of devices, and wherein the oneor more instructions, that cause the device to cause the networkrepeater to connect to the second base station, cause the device to:cause the network repeater to connect to the second base station toreduce the first load to prevent the first load from satisfying a secondload threshold that exceeds the first load threshold, wherein the firstbase station is configured to disconnect from one or more of theplurality of devices when the first load satisfies the second loadthreshold.